[DNS] Call out differences between standard vs advanced NS #23504
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryEnhanced documentation for advanced nameservers in Foundation DNS, highlighting differences from standard nameservers.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
This reverts commit 459ff3b.
|
This PR requires additional review attention because it affects the following areas: PartialsThis PR updates partial files, which are pieces of content used across multiple files in our Render component.
|
| | A | www | `192.0.2.1` | | ||
| </Example> | ||
|
|
||
| In this example, the TXT record and the A record for `www.example.com` will not be served. |
There was a problem hiding this comment.
Are we still using monospace for DNS record types? (e.g. TXT, A, AAAA, etc.)
There was a problem hiding this comment.
We added an exception for cases where there are several inline occurrences in a roll or for hyperlinks (since the style would make it look like two separate links). This was following a team critique a while ago.
Co-authored-by: Max Phillips <[email protected]>
* Introduce new limitations section for advanced NS * Expand to more general considerations and move to setup.mdx * Text review and add example DNS table for delegation * Re-add note on Advanced NS vs Custom NS to concept page * Use specific header for more emphasis and better linking * Nest DNSSEC keys under Advanced NS in Foundation DNS features * Add note on advanced ns vs custom in account-custom-nameservers * Further clarify advanced-vs-custom NS and align with UI messaging * Revert "Nest DNSSEC keys under Advanced NS in Foundation DNS features" This reverts commit 459ff3b. * Replace 'zone' by 'account' in features list * Create dedicated page explaining Foundation DNSSEC keys * Add clarification on how to get unique DNSSEC keys * Apply suggestions from code review Co-authored-by: Max Phillips <[email protected]> --------- Co-authored-by: Max Phillips <[email protected]>
2 participants
Summary
PCX-11801